The Lexmark*** Optra E*** LaserPrinter Installation Utilities This README.TXT file is for Utilities version 4.60 ------------------- README.TXT CONTENTS ------------------- - Overview - Diskette Contents - Compatibility and System Requirements - Running the Installation Utilities - User Tips and Recommendations - Problem Determination This text file provides additional information to help you use the Lexmark Optra E LaserPrinter Installation Utilities. If you need further technical assistance, contact your point of purchase or your Lexmark country representative. For Lexmark worldwide support contacts, refer to the text file, SOFTWARE.TXT, on this diskette. Also listed are technical support numbers for many software programs. README.TXT and SOFTWARE.TXT can be viewed using text editors such as NOTEPAD, included in Microsoft** Windows**, or EDIT, provided with DOS 5.0 or DOS 6.X, or you can print them on your Lexmark Optra E LaserPrinter in PCL** 5 Language. -------- OVERVIEW -------- The Lexmark Optra E LaserPrinter Installation Utilities and selected printer drivers for your LaserPrinter are provided on 2 diskettes included with your printer. These utilities and printer drivers are provided to help you set up and use the Lexmark Optra E LaserPrinter. Three key utilities are provided, Setup, Toolkit, and MarkVision*** for Windows. There are separate versions of the utilities for DOS (or Windows) users and for OS/2*. You can get the OS/2 version from the Lexmark Bulletin Board or from the Customer Fullfillment Center. See the SOFTWARE.TXT file for more information on the bulletin board and the telephone numbers. The Setup utilities for DOS, OS/2 and Windows quickly and easily set up your computer to use the Lexmark Optra E LaserPrinter. The functions provided are: - Verify printer to computer connection - Install printer drivers for selected software programs and environments - Install the printer Toolkits - Provide on-line help and contact numbers for Lexmark and many software program vendors The Toolkits for DOS, Windows and OS/2 are installed by their respective Setup Utilities for use at any time. The Toolkits include utilities to: - Print demonstration jobs (DOS and OS/2 only) - Format the flash memory - Load PCL macros into printer RAM or flash - Install Intellifont** for Windows and PCL 5 scalable screen fonts (supported in Windows and WIN-OS/2 only) - View, file, and send printer commands - Installation of the Network Printer Utility for Novell** NetWare** Networks is provided with the Lexmark Optra E LaserPrinter Network Option in the DOS Setup Utility. The MarkVision Printer Utility for Windows is installed by the Windows Setup utility. It offers operator panel functions at your Windows 3.1 workstation, and its graphical interface is easy to use. MarkVision: - Uses the bi-directional communication (NPAP 1.0) implemented in the Lexmark Optra LaserPrinter family of printers. (The bi-directional communication works only in Windows 3.1 running in 386 enhanced mode.) - Graphically displays printer errors, and offers help to assist in clearing them. - Ships with a PC-speaker driver and .WAV files to enable sound too! - Offers "drag-and-drop" file print capability to print to any of the printers being monitored by MarkVision. ------------------ DISKETTE CONTENTS ------------------ The Lexmark Optra E LaserPrinter Installation Utilities consists of 2 diskettes: - Windows Setup (Disk 1) * Contains Windows version of Setup and related files * Contains the Optra E driver for PCL 5 Language support in Microsoft Windows 3.1 * MarkVision Printer Utility for Windows 3.1 - DOS Setup (Disk 2) * Contains the DOS version of Setup and the Toolkit * Contains Lexmark Optra E LaserPrinter PCL 5 drivers for the DOS applications listed below. + Lotus** 123** Releases 2.3, 2.4, 3.1, 3.4 + Microsoft Works** 2.0, 3.0 + Microsoft Word** 5.5, 6.0 + Harvard Graphics** 3.0 + WordPerfect** 5.1 for DOS, 6.0 for DOS - OS/2 Setup (Through Lexmark BBS or Customer Fullfillment Center) * Contains the OS/2 version of Setup, Toolkit, and related files * PCL 5 OS/2 Driver for IBM OS/2 2.1 and higher * PCL 5 virtual printer files (also called printer colon files) for use with AIX Version 3.1.5 and AIX Versions 3.2 and higher. ------------------------------------- COMPATIBILITY AND SYSTEM REQUIREMENTS ------------------------------------- The Installation Utilities are designed to operate on IBM (or 100%- compatible) Personal Computers or Personal Systems with a hard drive and one high density (1.44 MB) 3.5" diskette drive. All the utilities were designed and tested for the following PC operating systems and environments: - PC-DOS or MS-DOS versions 5.0 or higher (To check your DOS version, enter the command, VER, at a DOS command prompt.) Prior DOS versions are not specifically supported; however, no compatibility problems are known. - Microsoft Windows 3.1 (Remember: bi-directional functionality within MarkVision only works with Windows running in 386 enhanced mode.) - IBM OS/2 versions 1.30.2 or higher (To check your OS/2 version, enter the command, SYSLEVEL, at an OS/2 command prompt.) Prior versions of OS/2 are not supported. To run the DOS version of the Utilities, a minimum of 390000 bytes of free memory is required. If you are running Microsoft Windows, you should close Windows before running the printer Setup utility. To verify that you have sufficient free memory to run Setup, enter the command, CHKDSK, at the DOS prompt. The value displayed for bytes free must be greater than 390000. See the PROBLEM DETERMINATION section below if you have less than 390000 bytes free. To run SETUP or SETUPWIN, you need at least 1 Megabyte of free hard disk space. This disk space will be freed when SETUP is complete. To install the Printer Toolkit, you will need at least 1.25 Megabytes of free disk space for each copy of the DOS or OS/2 version of the Toolkit you install. To install MarkVision, you will need an additional 2 Megabytes of free disk space. ---------------------------------- RUNNING THE INSTALLATION UTILITIES ---------------------------------- To run the Windows version of Setup: - Insert the diskette labeled "Windows Setup Disk" into drive a:. - In Program Manager, Select the File menu item. Select the Run option. - In the Run dialog box, type A:SETUP in the Command Line entry box. - Press Enter, and follow the directions displayed. To run the DOS version of Setup: - Insert the diskette labeled "DOS Setup Disk" into drive a:. - If you are running Microsoft Windows, you must first close Windows. - At a DOS command prompt, enter the command: A:\SETUP - Follow the directions displayed. To run the OS/2 version of Setup: - Obtain a copy of the OS/2 Setup Disk from the Lexmark Bulletin Board or from the Customer Fullfillment Center - Insert the diskette labeled "OS/2 Setup Disk" into drive a:. - At an OS/2 command prompt, enter the command: A:\SETUP - Follow the directions displayed. ----------------------------- USER TIPS AND RECOMMENDATIONS ----------------------------- - GENERAL The Installation Utilities diskettes may be copied for use with your LaserPrinter by using the DOS DISKCOPY command or its equivalent. Keep these diskettes with your printer and printer documentation. Do not copy the diskette labeled "Setup Disk" to a directory that contains another setup program. You should make backup copies of the Installation Utilities diskettes in the event your original diskettes are damaged during use. For best performance and access to all functions, the Toolkit for DOS and Windows should be installed on a local hard drive (physically attached to your system.) If the Printer Toolkit for DOS is run from a DOS window of OS/2, some toolkit functions will not be available. - CHOOSING EXPRESS VERSUS CUSTOM SETUP The Express method in Setup always searches all local (physically attached to your system) hard drives for all supported applications. Custom search allows you to select the search method for each application. Search methods include specific path, specific hard drive (including LAN drives), all local hard drives, or do not search. - INSTALLING BIDIDRVR.SYS FOR DOS Normally the bi-directional DOS Device driver is installed when the Printer Toolkit is installed. This device driver enables the Printer Toolkit to read flash and disk information from the printer during font downloads, for example. It also enables the Printer Toolkit Remote Operator Panel utility. Without the BIDIDRVR.SYS driver installed, the Remote Operator Panel utility does not work. NOTE: the BIDIDRVR.SYS device driver is NOT used for MarkVision functions. To install this device driver in DOS: 1) Using the SETUP DISK you first need to unpack the TKDOS.ZIP file onto your PC's hard drive: a:\pkunzjr a:\tkdos.zip c:\prt4026\ ... this assumes that you have a c:\prt4026 subdirectory before executing the above command. 2) Use the DOS EDIT utility to edit the CONFIG.SYS file. (EDIT C:\CONFIG.SYS) 3) Add the following line: DEVICE=C:\PRT4026\BIDIDRVR.SYS ... assuming that the BIDIDRVR.SYS file was unpacked into the C:\PRT4026 subdirectory. - WINDOWS DRIVER DISK 1 AND DOS DRIVER DISK 2 README.1ST FILES Each packed driver file on the DOS Setup Disk has a README.1ST file that contains useful information to assist in completing driver installation manually. That is, if the driver is unpacked using PKUNZJR or UNPCKDRV, the README.1ST file provides the instructions necessary to complete the manual installation of the driver. The OS/2 drivers have similarly named files that offer similar installation help. - CREATING PRINTER MACROS Printer overlay macros and demos can be created by printing a document to a file and then downloading the file to the printer with the Printer Toolkit. Keep in mind the following when creating printer macros: 1. Overlay macros should only be one page in length. All pages of a multiple page overlay will probably be printed on top of the page that invoked it. 2. The document that invokes an overlay should use the same printer resolution as the overlay itself. 3. A multiple page demo must be created with Fixups off, or it will be printed on one page. - AVOIDING DUPLICATE PCL FONTS IN FLASH AND DISK UNDER OS/2 To update both the Lexmark Optra E PCL 5 Language driver and the WIN-OS/2 Optra E PCL 5 driver with Flash font information and avoid duplicate entries in printer Flash memory, use the following sequence when downloading PCL 5 Language fonts to Flash memory: 1. Use the DOS Toolkit from a DOS command prompt in OS/2 to download PCL 5 Language fonts to Flash memory. The Font Installer of the Lexmark Optra E PCL 5 driver for Windows will be updated if the driver is installed and the "Always update Windows printer driver" setting is checked in the "Setup Font Environment" of the Toolkit Menu. 2. After downloading has completed, return to the OS/2 Desktop and update the flash font list in the OS/2 Optra E PCL 5 driver as follows: * Right click on the PCL 5-Lexmark Optra print object. * Left-click on the arrow beside Open, then left click on Settings. * Left click on the Printer Driver tab. * Left click twice on the IBMPCL5.Lexmark Optra object in the Default Printer Driver window. * On the Printer Properties panel, select Download Fonts. * On the Download Fonts panel, select Add and follow the directions to add the fonts to the driver that were downloaded to Flash memory. * When you return to the Download Fonts dialog, the fonts added to the driver will appear in the Download Fonts list. Make sure the Flash Memory Option box is checked. In the Flash Fonts list box, select the fonts downloaded to Flash in step 1 above. * Exit Download Fonts and Printer Properties by pressing OK on each. Close the Settings dialog. - DRIVER INSTALLATION WITHOUT THE DOS SETUP UTILITY ... USING UNPCKDRV You can unpack and install the printer drivers on the DOS Setup Disk if you do not have enough free memory to run the Setup Utility. A ZIP file unpack utility, UNPCKDRV.EXE, is included on the DOS Setup Disk. You may choose to use it instead of manually unpacking the files. The utility displays a list of ZIP files and will prompt you to choose both the file to be unpacked and the directory where the unpacked driver files are to be stored. Follow the steps below to unpack the ZIP-format files using UNPCKDRV.EXE. 1. Insert the DOS Setup Disk in the A: drive. 2. At a DOS command prompt, enter the command: A:UNPCKDRV 3. When the list of available ZIP files is displayed, enter the number of the file you have chosen to unpack. 4. When prompted, enter the destination directory. Please be sure to give the drive letter as part of the path, i.e. C:\DEST or D:\DEST1\DEST2. 5. After unpacking the chosen file, the program will allow you to select another file to unpack or exit. Press enter with no data entry to exit the program. 6. To install the driver in your software program, refer to the user's guide for your software application. NOTE: Unlike the Setup Utility, the UNPCKDRV.EXE program does NOT automatically update your software application. The program is provided for use by LAN Administrators or those who do not have sufficient memory to run the Setup Utility. - UNPACKING THE DRIVER FILES ... USING PKUNZJR If you cannot use the SETUP Utility or Printer Toolkit AND you cannot use the UNPCKDRV program discussed in the above section, you can unpack the driver files manually using PKUNZJR. See the table below to determine which files are needed for a specific software program, version, and printer language. Table of driver files on the DOS Setup Disk: -------------------------------------------- Files needed for Application PCL 5 Language --------------------- ---------------- Harvard Graphics 3.0 HG3026L5.ZIP Lotus 123 Rel 3.X LT3X26L5.ZIP Microsoft Word 5.5 WD5526L5.ZIP Microsoft Word 6.0 WD6026L5.ZIP Microsoft Works 2.0 WK2026L5.ZIP Microsoft Works 3.0 WK3026L5.ZIP WordPerfect 5.1 WP5126L5.ZIP WordPerfect 6.0 WP6026L5.ZIP Files with a file extension of ZIP are packed. They must be unpacked before the printer driver can be installed. Follow the steps below to unpack the ZIP-format files. 1. Insert Windows Setup Disk (for Windows drivers) or DOS Setup Disk (for DOS drivers) in the A: drive. 2. At a DOS command prompt, enter the command: A:PKUNZJR A:filename.ZIP drive:pathname\ where "filename" is the name of the driver file to be unpacked and "drive:pathname\" is a hard disk location where the files can be stored temporarily. 3. To install the driver in your software program, refer to the user's guide for your software program. OS/2 drivers on Driver Disk 3 do not need to be unpacked prior to installation. Refer to the user's guide for OS/2 or the printer software application guide for instructions on installing the OS/2 printer drivers. The Lotus 123 Rel 2.X drivers are located on the DOS Setup Disk. See the L2README.1ST file on the disk for instructions on manually installing these drivers. - DOWNLOADING PCL 5 FAIS FORMAT FONT FILES TO FLASH IN WINDOWS You can download scalable PCL 5 FAIS format fonts to your Lexmark Optra E LaserPrinter's Flash memory option using the Windows toolkit from MarkVision, the Dos toolkit or the OS/2 toolkit. The fonts downloaded to Flash are available for use by your software programs. - AIX SUPPORT Files supplied in the AIX subdirectory of the OS/2 Setup Disk (available from the Lexmark Bulletin Board or from the Customer Fullfillment Center) are for use with AIX Version 3.1.5 and AIX Versions 3.2 and higher. The virtual printer files (also called printer colon files) support PCL 5 Language of the Lexmark Optra E LaserPrinter. Browse, using a text editor, or print the file AIX_READ.ME in the AIX subdirectory of the OS/2 Setup Disk for more information and instructions. - NOVELL PRINTER DESCRIPTION FILE (PDF) A Novell NetWare Printer Description File (PDF), LEX4026.PDF, has been included on the DOS Setup Disk for the Lexmark Optra E LaserPrinter. See your Novell Netware documentation for information on using this file with the Netware PRINTDEF utility. - USING THE PRINTER TOOLKIT WITH NOVELL NETWARE Whenever possible, you should use the NetWare printer queues that appear in the Ports listboxes, rather than using the NetWare CAPTURE command with an LPT port. The Ports listbox should include all printer queues that the Toolkit finds while you are logged on. If you receive a message indicating "Error accessing ..." a specific NetWare printer queue, then you do not have proper network access. The network supervisor must grant at least Read/Search access under NetWare 2.x or Read/Filescan access on NetWare 3.x/4.x to the system binderies. If you must use CAPTURE, due to insufficient access rights or otherwise, then you should specify a timeout value of at least 5 seconds (/TI=5). For font downloads to work properly, you must also use a NetWare PRINTCON form that specifies Byte Stream instead of the default Text Stream. - MARKVISION FOR LAN SERVER/LAN MANAGER/WINDOWS NT SERVER ENVIRONMENTS The following tips and suggestions will help you to configure the MarkVision utility in the LAN Server/LAN Manager/Windows NT Server network environment. o MarkVision is optimized for the Windows for WorkGroups operating system, making use of its built-in networking features. MarkVision is supported, however, on Windows 3.1 systems (386 enhanced mode) using the DOS LAN Requester. The LAN Requester must be a version that provides an API interface. The following are support requester versions: - Microsoft LAN Manager Requester version 2.2B - IBM LAN Server DOS Requester 3.0 - IBM LAN Server Requester 4.0 o If you are running the DOS LAN Requester you will need to make the following changes to the DOSLAN.INI file: * Add the /API parameter. This will include support for the Applications Programming Interface required by the MarkVision application. * Add the /NMS:y parameter, where y is the number of "mail slots" to use. In general, y should be equal to the number of servers in your domain. Three is the minimum number that should be used. * Add the /NVS:y parameter, where y is the number of servers to "enumerate". Again, this number should be equal to the number of servers in your domain and three is the minimum number that should be defined. An example of these parameters in the DOSLAN.INI file is shown below: /API /NMS:5 /NVS:5 o If you are running the DOS LAN Requester and the Network Printer Utility does not show all of the servers on your domain, you may need to modify the DOSLAN.INI file as specified above. o At start up time, MarkVision will only attempt to attach to each server to which you are redirecting print jobs, that is, LPT ports that are redirected to queues on network servers. If you are an administrator and would like to attach to additional servers on the network, you can do this by adding the following line to the [LEXLLNET.DLL] section of your WIN.INI file: Server=servername. An example might be as follows: [LEXLLNET.DLL] Server=MORSE,TEST1 where MORSE and TEST1 are the names of the servers that you wish to attach to. Note that the more servers that are contained in this list, the more time that it will take for MarkVision to initialize. o If you are an administrator and would like to attach to all of the servers in your domain you can do this be adding the following line to the [LEXPANEL.DLL] section of your WIN.INI file: Enumerate Domain=TRUE. An example might be as follows: [LEXLLNET.DLL] Enumerate Domain=TRUE If there are many servers on your domain, this may significantly increase the amount of time that it takes for MarkVision to initialize. o Finally, MarkVision will create an additional entry in the [LEXLLNET.DLL] section of the WIN.INI file: Enumerated MV Servers. This entry is updated each time MarkVision is started and is a list of every server that MarkVision has previously attached to. - PPDS If your printer is code version 200A-x or higher, your printer is equipped with PPDS. (Your printer's code version is illustrated on the printer test page in the upper right corner of the page.) Additional information regarding activating and using PPDS is included on your DOS Setup Disk. To print this information, make sure your Optra E is connected properly to your host and type the following command at the DOS prompt (with the DOS Setup disk in drive A): copy a:ppds.txt lpt1 - PCL5E EMULATION COMMANDS A list of commonly used PCL5E emulation commands is included on the DOS Setup Disk. To print this file, make sure your Optra E is connected properly to your host and type the following command at the DOS prompt (with the DOS Setup disk in drive A): copy a:pcl4026.prn lpt1 --------------------- PROBLEM DETERMINATION --------------------- - NOT ENOUGH MEMORY TO RUN DOS SETUP OR TOOLKIT If the message, "You do not have enough memory to run the utility", appears when you try to run Setup or Toolkit, you must increase the amount of free memory in your DOS session. Setup or Toolkit for DOS requires a minimum of 390000 bytes of free memory. To check the amount of free memory, enter the command, CHKDSK, at the DOS prompt. The value displayed for bytes free must be greater than 390000. To increase the amount of free memory, try the following: * Close Microsoft Windows if it is running. * Terminate a Memory-Resident or TSR program. * Use the LOADHIGH command to run a Memory-Resident or Terminate and Stay Resident (TSR) program in the upper memory area. * Use HIMEM or EMM386 if your system has extended or expanded memory. If you are unable to obtain more than 390000 bytes of free memory, you you will not be able to run Setup. See "Driver Installation Without the Utilities" in the Helpful Hints section above. - INSUFFICIENT MEMORY PROBLEMS WHILE RUNNING MARKVISION While running Windows For Workgroups, MarkVision may have insufficient memory to operate properly. To help alleviate this problem, free as much conventional memory as possible by loading DOS and all possible TSRs in high memory. This can be accomplished by following the same procedures above for memory problems with Setup or Toolkit, or by using some other memory management program. Note that the amount of free memory required to run Setup or Toolkit does not necessarily apply to MarkVision. - MOUSE NOT WORKING Setup and Toolkit for DOS support mouse input. To enable mouse support, load the mouse driver provided with your mouse before using Setup or Toolkit. - RED ERROR BAR GENERAL RECOVERY RULES IN THE DOS UTILITIES Most DOS printer utility messages are displayed as a dialog box. On some error conditions, the bottom status bar turns red and the message, Esc=CANCEL or Enter=RETRY, appears. In general, it is best to press Enter to retry these error conditions. The Utility may end abruptly if you press Esc to CANCEL. - CRITICAL DISK ERROR USUALLY MEANS WRITE-PROTECT ERROR Critical Disk Errors when using the DOS Utilities are typically due to the diskette or Network Drive being Write-Protected. - OS/2 DRIVER WILL NOT INSTALL BECAUSE EXTENDED ATTRIBUTES WERE REMOVED If OS/2 driver installation fails because the Extended Attributes (EAs) were not present, run PCL5JOIN on the OS/2 Setup Disk, then retry the installation. Please see PCL5READ.ME on the OS/2 Setup Disk for further information. - LOGICAL OS/2 PORTS AND LAN PORTS NOT FOUND BY DOS UTILITIES When running the DOS utilities in the DOS box of OS/2 1.3 or 2.0, only physical printer ports will be found. Logical OS/2 ports and LAN ports will not be found and, therefore, cannot be used inside the utilities. - BI-DIRECTIONAL COMMUNICATIONS DOES NOT WORK FOR A SERIALLY CONNECTED PRINTER The Printer Toolkit will not support bi-directional communications to a printer connected to a serial port of your PC workstation. This includes the Printer Op Panel and Download Fonts functions of the Printer Toolkit. This also includes MarkVision. COMx connected printers will be listed as available on the MarkVision main screen, but they will never appear as bi-directional printers. - PC3270 FOR WINDOWS AND MARKVISION Memory errors reported by PC3270 for Windows can be avoided when running the MarkVision Utility if PC3270 is started BEFORE the MarkVision utility. - INSTALLING OLDER VERSIONS OF MARKVISION Some problems may be encountered if MarkVision for the Lexmark Optra E LaserPrinter is installed on a system and then, at some later time, an older version of MarkVision is installed in some other directory. This can cause problems because installing MarkVision for the older version will replace (with older versions) some of the code components required by the previously installed version of MarkVision. SINCE MARKVISION FOR THE LEXMARK OPTRA E FULLY SUPPORTS OLDER VERSIONS, THERE SHOULD NEVER BE A NEED TO INSTALL MARKVISION FOR AN OLDER VERSION ONCE MARKVISION FOR THE LEXMARK OPTRA E IS INSTALLED. - MARKVISION "FILE ERROR" MESSAGES ... "THE FILE XXXXXXX.DLL CANNOT BE FOUND" Your Optra version of MarkVision is capable of working with all previously released Lexmark Printers that support MarkVision. (i.e. 4039 plus and Lexmark 4079 plus) However, all the files necessary to support these printers were not included on your Optra diskettes, as for most people, this would waste diskette space. For example, if you install MarkVision for a 4079plus and then you installed the Optra MarkVision afterwards, you would not have any problems; AS LONG AS YOU DID NOT OVERRIDE the directory setting automatically selected by the Windows Setup Utility. If you overrode the directory where the Optra MarkVision was installed, MarkVision will no longer be able to find all its components enabling it to work properly for previously installed Lexmark Printers. If you overrode the directory on installation, re-install MarkVision into the directory where the first installed version exists. This will eliminate the "FILE ERROR" messages. Another way you could be getting these messages is if you are on a network, and as part of MarkVision's startup, it finds other Lexmark printers on the network, along with your Optra printer. You can ignore these messages as they do not keep MarkVision from working with your Optra printer, or you can get the required files by contacting Lexmark Technical Support or by downloading the appropriate files from the Lexmark BBS system. You can find these phone numbers in the SOFTWARE.TXT file in your MarkVision subdirectory. The MarkVision upgrade files are on the BBS in MVWN3x.EXE. - USING YOUR COMPUTER'S ECP AND UNIQUE IRQ'S WITH MARKVISION Bi-directional communication problems while using MarkVision can happen for a variety of reasons. One reason may be due to the use of your PC's parallel port interrupt service IRQ. MarkVision now supports IRQ5 in addition to IRQ7 for LPT ports. IRQ7 support is still the default. To enable IRQ5 for a particular LPT port, two things have to be done. First place the following entry in your SYSTEM.INI file anywhere in the [386Enh] section: MVLPTXIrq=5 (The string is case sensitive.) ... where 'X' represents your LPT number, e.g., 1, 2, or 3. Next the IRQ setting for the corresponding LPT hardware must usually be set to match the SYSTEM.INI entry. For LPT2 and LPT3, the IRQ is generally set by removing the LPT adapter card from your PC and changing a jumper block. See the adapter card documentation. For LPT1, the IRQ may or may not be settable. The PC's BIOS setup should be run to determine if the IRQ is settable. The BIOS setup can be invoked by depressing a key during power up time on most PC's. For the above entries in your SYSTEM.INI file to take effect, Windows must be restarted. MarkVision supports the IEEE 1284 ECP protocol. This is a relatively new protocol implemented in hardware on a small number of PC models at the time this product was released; therefore, as new PC models implement ECP in their hardware, MarkVision's ECP support may or may not be compatible with them. MarkVision's default operation is to sense if ECP hardware is present on the system and use it if found. If you experience any problems with your MarkVision/printer operation, ECP can be disabled by placing the following string in the [386Enh] section of SYSTEM.INI: MVDisableECP=1 (The string is case sensitive.) If MarkVision finds the string during Windows startup time, ECP will not be used. NOTE: See the online MarkVision help for other reasons why bi-directional communications may not be working. - WINDOWS FOR WORKGROUPS 3.11 PRINT MANAGER NOT FUNCTIONING WHEN 13+ DRIVERS ARE INSTALLED It should be noted that the Windows for Workgroups 3.11 Print Manager does not support more than 13 printer drivers installed at one time. - MARKVISION INSTALL DOES NOT REMOVE MARKVISION AT STARTUP If you are re-installing MarkVision and select not to run MarkVision at startup, the Installer will not remove any MarkVision executions at startup created by previous installations. To remove MarkVision at startup, open your Startup group icon, select MarkVision and enter . This will remove MarkVision from Windows startup. - AVOIDING WINDOWS DRIVER ERROR MESSAGES DURING DRIVER INSTALLATIONS You should not attempt to install any Windows printer drivers using the DOS Printer Toolkit "Update Printer Drivers" facility, when running MarkVision. Attempting to do this will cause Windows error messages to appear, and you will not be successful. You need to first exit Windows and start the Printer Toolkit with the DOS command TOOLKIT. From here you can update the Windows printer drivers. When complete, restart Windows. NOTE: this is only a problem with Windows driver installations. Other DOS application drivers can be installed, and nearly all other Toolkit functions can be performed while MarkVision is running. - APPLICATION LANGUAGE NOT SUPPORTED FOR MICROSOFT WORD & WORKS During application driver installation, you can receive a message that states that the language of the application is not supported and that the driver for that application cannot be installed. This can occur with Microsoft Word 5.5, 6.0 & Works 2.0, 3.0. The most typical cause for this problem is that when the application was installed, no printer driver (of any kind) was installed. A previous printer driver must have been installed for these applications in order for the utilities to recognize the language type. To remedy the problem, manually install any printer driver into the application first, then use the utility to install the new printer drivers. ========================================================================== PCL is a U.S. registered trademark of the Hewlett-Packard Company. IBM is a registered trademark of the IBM Corporation. Terms identified by a single asterisk (*) are trademarks or registered trademarks of the IBM Corporation. Terms identified by a double asterisk (**) are trademarks or registered trademarks of their respective companies. Terms identified by a triple asterisk (***) are trademarks or registered trademarks of Lexmark International, Inc. END OF RDME4026.TXT